A Final Destination is the ultimate goal of an Entity’s journey through a model. It is usually an Exit but can also be a Waiting Zone (in the case of stadium ingress studies, for example). A 'group object' can also function as a Final Destination. In the absence of any other routing information or links to intermediate objects, an Entity will proceed through the model to its Final Destination.

Final Destinations can be imported into a model using the Data Template spreadsheet, which can, from the OD matrix, create parameters to be used by Entrances (including Final Destinations).

Final Destinations can also be assigned manually at any stage in the model building process; basically, any existing Exit or Waiting Zone can be used in a Demand Line as a Final Destination.

Entities can have intermediate targets, which can be manually placed as links between spatial objects. Final Destinations are only considered when there are no more intermediate targets for an Entity to try to reach.

So, if you have an Entrance that links to a Focal Node but also has an Exit as its Final Destination, all Entities introduced to the model through the Entrance will initially travel to the Focal Node but once they leave there, assuming there are no further manual links from the Focal Node to other objects, they will resume their journey to their final destination.

It is not necessary for every Entity to have a Final Destination, as long as they always have some kind of routing information and are linked at some point to an Exit or a Waiting Zone. This means that models created before the release of LEGION Model Builder will work perfectly well, even though they have no concept of Final Destinations.